Summary

This PR completes Zeo (washing machine) device support in python-roborock.

The library already had foundational A01 protocol support for Zeo devices, but several critical gaps prevented practical use: the start command didn't work, roughly half of the DP IDs were undefined, several device states and enum classes were missing, and most data points had no value converters. This PR closes those gaps, bringing the DP and enum definitions in line with the Roborock Washer app protocol.

With these changes, Zeo devices support the full range of operations defined by the protocol: start/stop/pause/shutdown, mode and program selection, temperature, rinse, spin, drying control, child lock, auto detergent/softener, UV sterilization, soak, silent mode, dry care, steam, ion deodorization, wash-dry linkage, and more.

Motivation

The library's existing Zeo set_value(START, 1) did not actually start the device. Through protocol analysis and comparison with the Roborock Washer HomeAssistant integration, three root causes were identified:

1. QoS level: DP200 must be published at QoS 1; the default QoS 0 was rejected by the broker.
2. Missing timestamp: A01 command payloads require a "t" (Unix timestamp) field.
3. Missing parameter bundle: The device firmware requires MODE and PROGRAM to be sent together with START in a single MQTT message.

Beyond the start command, RoborockZeoProtocol covered only 31 of 67 known DP IDs, zeo_code_mappings.py was missing 4 enum classes and several enum values, and ZEO_PROTOCOL_ENTRIES provided converters for only 16 of the 52 user-facing DPs — meaning query_values() silently returned None for most data points.

Changes

1. MQTT QoS — roborock/mqtt/roborock_session.py

Changed client.publish() to use qos=1 (at-least-once delivery).

2. A01 payload timestamp — roborock/protocols/a01_protocol.py

Added "t": int(time.time()) to the JSON payload structure in encode_mqtt_payload().

3. Combined start command — roborock/devices/traits/a01/__init__.py

ZeoApi.set_value(START, 1) now:

• Queries the device for its current MODE, PROGRAM, TEMP, RINSE_TIMES, SPIN_LEVEL, and DRYING_MODE
• Bundles the returned values with {START: 1} into a single MQTT message
• Falls back to MODE=1, PROGRAM=1 if the query fails

4. Extended DP ID enum — roborock/roborock_message.py

RoborockZeoProtocol expanded from 31 to 67 entries, now covering all 52 user-facing DPs (200-266) plus meta DPs. Newly added: dirt detection (215-216), UV light (228), soak (233), total time (234), smart hosting (235-238), silent mode (240-242), dry care mode (244), wash-dry linkage (255), drying method (256), steam volume (257), ion deodorization (258), dryer start error (265), and more.

5. Enum updates — roborock/data/zeo/zeo_code_mappings.py

• ZeoMode: added treatment = 4
• ZeoState: expanded from 13 to 20 states
• ZeoSoak: added very_max = 5
• New enum classes: ZeoDryingMethod, ZeoSteamVolume, ZeoDryAndCare, ZeoDryerStartError

6. Value converters — roborock/devices/traits/a01/__init__.py

ZEO_PROTOCOL_ENTRIES expanded from 16 to 57 entries, providing typed converters for all user-facing DPs (200-266).

Backward Compatibility

All changes are additive or transparent:

• ZeoApi.query_values() and ZeoApi.set_value() signatures unchanged
• New DP IDs and enums are pure additions
• QoS change applies to all MQTT publishes, matching the expected at-least-once delivery
• Start command query adds ~1-2s latency; all other set_value calls unaffected

Known Limitation

sent_decoded_command uses a strict "all requested DPs must respond" completion condition. Since A01 devices do not expose a capability probing mechanism, there is currently no clean way to determine which optional DPs (e.g., SOAK, STEAM_VOLUME) a given device supports before querying them.

As a temporary workaround, the start command queries and bundles only the following 6 core DPs, which has been verified to successfully start devices on physical Zeo hardware:

These are bundled with {START: 1} and sent as a single MQTT message. The device applies its internally-stored values for any parameters not explicitly included.

A better long-term solution for dynamically detecting device capabilities is welcome — contributions or ideas in this area are appreciated.

Testing

• set_value(START, 1) verified working on physical Zeo One and Zeo M1S devices
• set_value for non-START DPs (mode, program, temperature, etc.) continues to work as before
• Coordinator polling and DPS push updates unaffected
• All changes pass linting (ruff, mypy)

Acknowledgments

This PR draws heavily on the excellent reverse-engineering work done in ndwzy/roborock_washer_ha. The A01 protocol structure, DP definitions, enum mappings, and the combined start command behavior were all cross-referenced against that project's implementation. The DP ID list (200-266), state enum values, and device error codes were verified against the Roborock app bundle extracted and analyzed by that project.

Closes #833